home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
BBS Toolkit
/
BBS Toolkit.iso
/
doors_1
/
jlut500.zip
/
HLP.ZIP
/
CM.HLP
< prev
next >
Wrap
Text File
|
1992-02-11
|
3KB
|
73 lines
┌────────────────────────────┐
│ Option: CM CHECK MESSAGES │
└────────────────────────────┘
┌─Explanation────────────────────────────────────────────────────────────────┐
└────────────────────────────────────────────────────────────────────────────┘
Sometimes a User miss-spells the name of the recipient of a message. If
he marks it private, he will never get an answer. Of course he is
waiting for one and perhaps he writes the message again. If you have
a small BBS and only a few Users, you can check the Names manually,
but even then it is time intensive. And can you ever be sure, that you
have detected every message with a miss-spelled ReceiverName ? Most
probably you are normally very busy and why shouldn't you let JLUTIL
do this work.
This Option is doing a great job and if you run it within a NetMail
Area, it will inform the Sender of a Message perhaps thousands miles
away, that there is no User at your BBS with the ReceiverName, he has
specified. And now you will ask, if you can manipulate the message,
the MCS will send to the Sender. Of course you can. The name of the
message is specified in JL.CNF. Read GENERAL.HLP for more
informations. If the MCS detects a message with an unknown receiver,
it will change the ReceiverName to 'UNKNOWN RECEIVER'.
Now you ask, and if there is somebody writing a message to ALL or
to Sysop ? This option is checking only private messages and if
somebody writes a private message to ALL, it remembers the Sender
that his message will never be read. So you can run this Option
in all MsgAreas, even in EchoAreas. This option skips messages too,
which have been received already.
And what is, if the Sender is a program ? This option answers only
messages of people, who haven't been listed in the NOANSWER.@JL
File.
And what happens, if the Sender of a local entered message is unknown ?
Then JLUTIL will kill this message.
You see, this option is a fine one and you should run it daily
within all areas. And because you must save time, you should use
the switch, which saves the last scanned message.
┌─Syntax─────────────────────────────────────────────────────────────────────┐
└────────────────────────────────────────────────────────────────────────────┘
JLUTIL /CM [MsgArea] [-Switches]
┌─Switch──────Description────────────────────────────────────────────────────┐
└────────────────────────────────────────────────────────────────────────────┘
-P Reads and writes the position of the last scanned message.
-S Kills a message, if the sender is unknown.
┌─Parameter───Description────────────────────────────────────────────────────┐
└────────────────────────────────────────────────────────────────────────────┘
MsgArea Specify the MsgArea, which should be scanned, or '*' for
all MsgAreas. Read GENERAL.HLP for possible settings like
'?' or '~'.
┌─Examples───────────────────────────────────────────────────────────────────┐
└────────────────────────────────────────────────────────────────────────────┘
JLUTIL /CM ?
JLUTIL /CM E:\GT\MSGLOGON
JLUTIL /CM ~ -P